I decided to go back and review the whole thread again to make sure that I didn't misread anything the first time. I may have misunderstood some things. Apologies, especially to ASWC. el111  wrote An update to an app must work for every customer who has already purchased the app, and is running a current version of iOS. Developers who wish to issue updates, but remove device support, have three choices: Target a newer version of iOS that requires a newer device. See Targeting the Latest iOS for details. Does this indicate that a current universal app that supports both 32-bit and 64-bit architectures can be updated to 64-bit only without changing the bundle ID as long as it targets a version of iOS that doesn't support 32-bit devices anymore? If that's the case, users with old 32-bit devices would be stuck on an old version, but users with 64-bit devices would still get updates to the existing app. Right? I was under the impression that no apps originally built with AIR 29 or older could be updated with AIR 30 or newer because Apple's policy is that you can't drop support for older devices. However, it seems that Apple allows you to exclude devices that can't upgrade to the minimum version of iOS that you are targeting. If that's the case, then this is not as serious an issue as I originally thought. (Don't get me wrong, if Apple still allows you build universal apps that also support 32-bit devices in Xcode, I think AIR should continue to support that too. However, I'd also understand if the AIR team didn't have the resources to continue to support the dwindling number of 32-bit iOS devices still in use.) Considering how easily this gets confusing, I think the AIR 30 release notes need to include more details. If I want to update an existing AIR app that was released before AIR 30, do I need to do anything to set the minimum iOS version in my AIR application descriptor when I repackage with AIR 30? Or does AIR 30 do everything automatically? If it doesn't happen automatically, the release notes absolutely need to include instructions on how to do it manually. Even if it is automatic, the release note should probably say that explicitly to avoid any more confusion. ... View more

ASWC  wrote Ok then if it's the case I will retract all my statements. But someone please explain to me why the EVENTUAL complete drop of 32bits support by Apple will not put everybody in the same situation? Presumably, if Apple were to drop all support for universal apps that contain 32-bit code, they would provide a migration path for the millions of existing native apps that are currently universal. ... View more

ASWC  wrote Are you saying if Adobe supports 32bits until the last moment when Apple pulls the plug on it nobody will have to face all the problems you are listing here? Is that "serious problem" going to go away forever once Adobe complies with the request here and support 32bits until Apple doesn't? As far as I understand the situation, yes. ... View more

cybobear  wrote Honestly, don't even read zwetan_uk's posts, he's redundant and ignores what's being said. It's just going to hurt your brain. The guy is seriously obtuse. zwetan_uk, for a guy with some pretty terrible English it's cute how condescending you are. I bet you fail hard at most interviews. Please try to avoid personal attacks. This goes for everyone replying here. Stay on topic and ignore anyone who isn't helpful. Everyone who has replied here is getting notifications, so let's try to keep the signal high and the noise low. ... View more

ASWC  wrote Why a "serious issue"? We can publish our new updated 64bits only as new apps which is something many have had to do before for number of reasons anyway. It's annoying sure but really serious issue? I'd call that much more than annoying. You're saying that thousands of AIR developers that want to update their apps that were originally built with AIR 29 or below will each need to publish a completely new app instead of updating their existing app? They'll need to try their best to inform their existing users that they need to uninstall the existing app and download the new app instead. They'll definitely get stuck with a ton of users on an old version. Some will abandon the app because it's too much effort to search for the new version, even if they liked the app. If the app was paid, do you just offer it for free for a couple of days so that your existing users don't need to pay again? I've seen a temporary discount for a new "major" version before, but it's one thing when you make that choice yourself, and it's another when you're forced to do it because Adobe made a poor choice. ... View more

I've seen a few people claiming that Apple has specifically announced that apps must be 64-bit-only for iOS (not talking about Mac here), and I'd like to see that Apple has in fact specifically made that statement As far as I can tell, Apple is not requiring 64-bit only apps on any platform. I've not seen any policy updates from Apple that forbid universal apps that support both 64-bit and 32-bit architectures. Soon, 32-bit only apps will not be allowed on macOS. I believe that a similar policy has been effect for a while now where 32-bit only apps were not allowed on iOS. The concerns brought up in this thread are completely valid, as I understand it. Developers will be in a bad place if Adobe AIR goes 64-bit only on iOS, and it's not their fault in any way. According to the Apple policy previously cited in this thread, if an iOS app already supported 32-bit devices, it cannot be updated with a new build that supports only 64-bit devices. To update this app, it must be a universal app that supports both 32-bit and 64-bit devices. With the current version of AIR 30, that seems to be impossible, which is a serious issue. ... View more

@chaky\ Speaking of keeping things professional, try to stop throwing around the R word here. I understand that you're dealing with some strangely antagonistic replies here, but I think it's better to just try to stay on topic and ignore anyone who isn't actually helping. Not everyone deserves a response. ... View more

When feather is not updated to AIR 29, that sentence is a beauty ... I could be a medium with superpowers when I say everything will be fixed once starling and feather run their next update ... But what do I know right? This is not helpful or professional. How about we take things down a notch? I don't see anything obvious in the AIR 29 beta release notes to indicate that Feathers (or Starling) might need to be updated for masking to continue working correctly. While Stage 3D profiles were suggested, and the release notes say that the ENHANCED profile has been added to desktop, chaky\ says that's not the profile being used. With all that in mind, as the developer of Feathers, I would not expect to have to update anything in my library to remain compatible with the new version of AIR. This certainly seems like a bug in AIR 29 beta to me. With a beta build, it should be unsurprising that new bugs might be introduced. ... View more

I know that this is a very old thread, but I can add some information that might be useful if someone runs into the same issue today. The AIR SDK & Compiler contains a file named asc-support.swc that includes the definition for flash.compiler.embed.EmbeddedMovieClip. You can find this file at [AIR SDK path]/frameworks/libs/asc-support.swc. The SWF that you are embedding was probably built with the AIR SDK & Compiler. If your project in Flash Builder 4.7 is an ActionScript project (not a Flex project), it probably also uses the AIR SDK & Compiler when it creates a release build, so this class will be present. However, if your build script uses the Flex SDK to compile, that could explain why flash.compiler.embed.EmbeddedMovieClip is missing. I don't see asc-support.swc in the Flex SDK, and I suspect that it isn't in any other SWCs either. I'll bet that the "asc" in asc-support.swc refers to the ASC 2.0 compiler, which is the new compiler used by the AIR SDK. The Flex SDK has a different compiler, and it uses some different classes, notably mx.core.MovieClipAsset, when it embeds assets. Anyway, if you're trying to build an app with the Flex SDK, and you get this error, you might try grabbing asc-support.swc from the AIR SDK & Compiler and adding it to your library path. Another option would be to skip the Flex SDK entirely (as long as you're not using MXML and the Flex framework, of course) and compile with the new compiler in the AIR SDK & Compiler instead. ... View more

I'm not sure that's correct, Colin. When they announced that renderMode gpu would be deprecated, I'm pretty sure that they said that they weren't going to actively maintain it anymore, but they also wouldn't be removing it either. Basically, use at your own risk. ... View more

swfisgood is correct. The renderMode GPU that is available on AIR mobile was never available on desktop. ... View more

According to the Adobe roadmap for the Flash runtimes: Given [...] the growing importance of browser-based virtual machines, Adobe will focus its future Flash Player development on top of the existing Flash Player architecture and virtual machine, and not on a completely new virtual machine and architecture If you're hoping to see a new VM, I'd say that it's safe to say that you will be disappointed. As I recall, they were developing AS4 because they couldn't build a significantly better VM based on AS3. ActionScript's ECMAScript legacy requires some performance overhead that cannot be avoided. You can cite the increasing performance of JavaScript as a counter-argument, but AS3 also includes things from the abandoned ECMAScript 4 spec that modern JavaScript never needs to deal with. If I remember correctly, Adobe engineers cited support for namespaces (beyond the core public/private/protected/internal) as one feature that adds significant overhead to basically everything running in AVM2. I remember that there were a number of AS3 features that were like that. I'm afraid that I don't really remember specifics beyond that. It's been a long time. That's not to say that the current AVM can't be improved. I imagine that there are little wins here and there, but you really shouldn't hold out hope for anything huge. ... View more

It would be great if this had an option like Android's "adb install -r" to install an app even if it is already installed on the device. Otherwise, I get the error "Failure ". ... View more

When I saw that error message, I tried starting up the command line with "Run as administrator". It went away after that. ... View more